home *** CD-ROM | disk | FTP | other *** search
- Path: aargh.incubus.sub.org!marc
- From: marc@aargh.incubus.sub.org (Marc 'Nepomuk' Heuler)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Demo/game to OS friendly part II
- Message-ID: <MWxUx*oha@aargh.incubus.sub.org>
- Date: Sat, 06 Jan 1996 11:32:00 CET
- Reply-To: marc@aargh.incubus.sub.org
- References: <38231819@kone.fipnet.fi> <4ch9ht$hpf@sunsystem5.informatik.tu-muenchen.de>
- Distribution: world
- Organization: Data Design
- X-Newsreader: Arn V1.03a
-
- In article <4ch9ht$hpf@sunsystem5.informatik.tu-muenchen.de>, Juergen "Rally" Fischer writes:
-
- > Is this legal:
- > In a user coperlist I direct copper to my own copperlist via copjmp2 to
- > get copper controll (modifiable copperlist). The question is if future
- > OSes won't use copjmp2 in a unexpected way ?
-
- Nice trick. Although not really system compliant, I won't cause too much
- trouble.
-
- However, I strongly advise you open your screen
-
- EITEM SA_Exclusive ; New for V39:
- ; Boolean tag allowing screens that won't share
- ; the display. Use sparingly! Starting with 3.01,
- ; attached screens may be SA_Exclusive. Setting
- ; SA_Exclusive for each screen will produce an
- ; exclusive family. (Defaults to FALSE).
-
- (OS won't _try_ to mix your copperlist with someone elses')
-
- and declare it not draggable.
-